Integrated electronic commerce system and method

ABSTRACT

An integrated electronic commerce system ( 10 ) may include a server system ( 12 ) comprising a plurality of electronic commerce applications ( 44 ) and a server security system ( 46 ). The electronic commerce applications ( 44 ) may comprise an electronic mail application ( 52 ), a web server application ( 54 ), and a file transfer application ( 56 ). The server security system ( 46 ) may validate a client system ( 14 ) and download information operable to enable a service manager ( 90 ) of the client system ( 14 ) to invoke the electronic mail application ( 52 ), the web server application ( 54 ), and the file transfer application ( 56 ) to send and receive data over a network ( 18 ).

CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application is a continuation of U.S. patent applicationSer. No. 08/892,580 filed Jul. 14, 1997 and entitled “INTEGRATEDELECTRONIC COMMERCE SYSTEM AND METHOD”.

TECHNICAL FIELD OF THE INVENTION

[0002] This invention relates generally to the field of electroniccommerce, and more particularly to an integrated electronic commercesystem and method.

BACKGROUND OF THE INVENTION

[0003] Electronic commerce (EC) is a way to electronically conduct andmanage business transactions using computer and telecommunicationsnetworks. It provides participants with efficient methods of workingwith customers, suppliers, and other trading partners. Network-basedelectronic commerce may include simple transactions, such as electronicmail and facsimiles, and more complicated transactions, such aselectronic data interchange (EDI), electronic funds transfer (EFT), andshared network resources. Electronic data interchange and electronicfunds transfer transactions create opportunities for companies toshorten procurement cycles and to cut costs on inventory and manufactureparts through the use of just-in-time (JIT) and quick response (QR)practices. Shared network resources allow companies to acceleratetime-to-market cycles through collaborative development and productcustomization.

[0004] Resources to support complicated electronic commerce servicessuch as electronic data interchange, electronic funds transfer, andshared resources are expensive. Additionally, the resources are oftensegregated into specialized systems. As a result, access to complicatedelectronic commerce services has traditionally been limited to largerbusiness. The lack of smaller business participation in such servicesreduces the efficiency of the smaller business and the value of theservices to the larger business.

SUMMARY OF THE INVENTION

[0005] Accordingly, a need has arisen in the art for improved electroniccommerce services. The present invention provides an integratedelectronic commerce system and method that substantially reduce oreliminate disadvantages and problems associated with prior systems.

[0006] In accordance with the present invention, an integratedelectronic commerce system may include a server system comprising aplurality of electronic commerce applications and a server securitysystem. The electronic commerce applications may include an electronicmail application, a web server application, and a file transferapplication. The server security system may validate a client system anddownload information operable to enable a service manager of the clientsystem to invoke the electronic mail application, the web serverapplication, and the file transfer application to send and receive dataover a network.

[0007] More specifically, in accordance with one embodiment of thepresent invention, the information downloaded to the client system maycomprise an electronic mail identifier, a file transfer identifier, anda browser identifier. The electronic mail identifier may enable theservice manager of the client system to invoke the electronic mailapplication. Similarly, the file transfer identifier may enable theservice manager to invoke the file transfer application. The filetransfer application may send and receive electronic data interchange(EDI) data, electronic funds transfer (EFT) data, and the like over thenetwork.

[0008] The browser identifier may enable the service manager to invokethe web server application. The web server application may send andreceive data over public and private networks. Public networks mayinclude the Internet. Private networks may include value added networks(VAN) such as an intranet or an extranet.

[0009] Technical advantages of the present invention include providingan integrated electronic commerce system. In particular, the client mayaccess a plurality of electronic commerce systems from an integratedservice manager. This allows clients to electronically conduct businessfrom a simple interface having a single point of entry.

[0010] Another technical advantage of the present invention includesproviding relatively low cost electronic commerce services. Inparticular, the client may access electronic commerce services through aserver system. The server system may include an electronic mailapplication, a web server application, and a file transfer application.Accordingly, the client may efficiently and inexpensively send andreceive data over a network. The data may include electronic datainterchange (EDI), electronic funds transfer (EFT), and the like.

[0011] Other technical advantages will be readily apparent to oneskilled in the art from the following figures, descriptions, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] For a more complete understanding of the present invention andits advantages thereof, reference is now made to the following briefdescription, taken in conjunction with the accompanied drawings anddetailed description, where like reference numerals represent likeparts, in which:

[0013]FIG. 1 is a schematic diagram illustrating a client system and aserver system connected via a network in accordance with one embodimentof the present invention;

[0014]FIG. 2 is a schematic block diagram illustrating components of theclient and server systems of FIG. 1 in accordance with one embodiment ofthe present invention;

[0015]FIG. 3 is a flow diagram from a client's perspective illustratingthe process of conducting electronic commerce in accordance with oneembodiment of the present invention;

[0016]FIG. 4 illustrates a graphical user interface (GUI) window forconducting electronic commerce in accordance with one embodiment of thepresent invention;

[0017]FIG. 5 is a flow diagram illustrating a method of providingintegrated electronic commerce services over a network in accordancewith one embodiment of the present invention;

[0018]FIG. 6 is a flow diagram illustrating a method of uploading andtransmitting a client file over a network in accordance with oneembodiment of the present invention; and

[0019]FIG. 7 is a flow diagram illustrating a method of receiving anddownloading a data file to a client in accordance with one embodiment ofthe present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0020] The preferred embodiments of the present invention and itsadvantages are best understood by referring now in more detail to FIGS.1-7 of the drawings, in which like numerals refer to like partsthroughout the several views. FIGS. 1-7 illustrate a system and methodof providing electronic commerce over a network. As described in moredetail below, the system and method employ a client system having anintegrated service manager operable to open and use electronic commerceapplications of a server system to transmit electronic commerce over aseries of networks. Electronic commerce applications may includeelectronic mail, a file transfer system, and a browser. It will beunderstood that electronic commerce applications may comprise otherapplications in that the electronic mail, file transfer and web serverapplications are for illustrative purposes only. Accordingly, thepresent invention allows electronic commerce to be conducted from asingle point of entry.

[0021]FIG. 1 illustrates an integrated electronic commerce system 10 inaccordance with one embodiment of the present invention. The integratedelectronic commerce system 10 may comprise a server system 12 connectedto a client system 14 by a dedicated network 16. The server system 12may be a computer such as a personal computer, file server, workstation,minicomputer, mainframe or any other computer capable of communicatingand interconnecting with other computers. As described in more detailbelow, the server system 12 may include an input/output system,processor, and memory. The input/output system may connect the dedicatednetwork 16 and other input and output devices to the server system 12.The dedicated network 16 may be directly connected to the server system12 or may be connected through a data transmission device such as amodem or the like. In one embodiment, the dedicated network 16 maycomprise a modem connected to the client system 14 and a modem link tothe server system 12 via an access server connected to an internal widearea network to which the server system 12 is connected. The inputdevices may include a pointing device such as a mouse or trackpad, akeyboard, or the like. The output devices may include a monitor, aprinter, or the like.

[0022] The server system 12 may be connected to a plurality of networks18. As described in more detail below, electronic commerce may beconducted over the networks 18. In one embodiment, the networks 18 mayinclude a public Internet 20, one or more value added networks 22, andan X.400 electronic mail network. It will be understood that other ordifferent networks 18 may be connected to the server system 12 withinthe scope of the present invention.

[0023] Each network 18 may comprise a plurality of communication lines19. Communication lines 19 may be any type of communication link capableof supporting data transfer. In one embodiment, the communication lines19 may include any combination of an Integrated Services Digital Network(ISDN) communication line, a hardwire line, or a telephone link. It willbe understood that the communication lines 19 may comprise other typesof links within the scope of the present invention.

[0024] The client system 14 may be similar to the server system 12 andmay be implemented using virtually any type of computer. As described inmore detail below, the client system 12 is preferably a personalcomputer having an input/output system, a processor, and a memory. Aspreviously described for the server system 12, the input/output systemmay connect the dedicated network 16 and other input and output devicesto the client system 14.

[0025] The dedicated network 16 may include a plurality of communicationlines 28 between the server system 12 and a plurality of clients such asthe client system 14. The communication lines 28 may also connect tointermediate servers between the server system 12 and the client system14. Thus, a plurality of intermediate servers may be disposed betweenthe client system 14 and the server system 12 along communication lines28.

[0026] Communication lines 28 may be any type of communication linkcapable of supporting data transfer. In one embodiment, thecommunication lines 28 may include any combination of an IntegratedServices Digital Network (ISDN) communication line, a hardware line, ora telephone link. It will be understood that the communication lines 28may comprise other types of links within the scope of the presentinvention.

[0027] In one embodiment, the dedicated network 16 may comprise dialaccess via a telephone link. In this embodiment, the server system 12may be remote from the client system 14 and located anywhere in theworld. Generally described, the client system 14 may connect andcommunicate with the server system 12 via a modem. Dial access may bethrough a 1-800 telephone number. Preferably, the modem has a datatransmission rate of at least 9.6-28.8 kilobytes (Kb). It will beunderstood that a modem may have other transmission rates and thataccess may be otherwise obtained within the scope of the presentinvention. Moreover, although the dedicated network 16 is illustratedand described in FIG. 1 as dial access via a telephone link, thededicated network 16 may be any interconnection found on any computernetwork such as a local area network (LAN), a wide area network (WAN),or any other communications and data exchange systems created byconnecting two or more computers.

[0028]FIG. 2 illustrates a block diagram of the server system 12 andclient system 14 in accordance with one embodiment of the presentinvention. The server system 12 may comprise an input/output system 30,a processor 32 and memory 34. As previously described, the input/outputsystem 30 may connect the dedicated network 16 and other input andoutput devices to the server system 12. The dedicated network 16 may bedirectly connected to the server system 12 or may be connected through adata transmission device such as a modem or the like. Input devices mayinclude a pointing device such as a mouse or trackpad, a keyboard, andthe like. Output devices may include a monitor, a printer, and the like.

[0029] The server system 12 includes computer software that may beloaded into the memory 34 and executed by the processor 32. The computersoftware may generally be identified by modules and similar systems inmemory 34. It will be understood that the computer software may beotherwise combined and/or divided for processing within the scope of thepresent invention. Accordingly, the labels of the modules and othersoftware systems are for illustrative purposes and may be varied withinthe scope of the present invention.

[0030] The computer software may be loaded into memory 34 from diskstorage (not shown). Disk storage may include a variety of types ofstorage media. For example, disk storage may include floppy disk drives,hard disk drives, CD/ROM drives, or magnetic tape drives.

[0031] Memory 34 may include an operating system 40, a servercommunication system 42, a set of electronic commerce applications 44,and a server security system 46. The operating system 40 may include astandard UNIX interface 48. The operating system 40 may be UNIX, NVS, orthe like.

[0032] The server communication system 42 may, in conjunction with acounterpart on the client system 14, provide a communicationinfrastructure for the integrated electronic commerce system 10. In oneembodiment, the server communication system 42 may comprise TCP/IP whichis the primary communications protocol for a UNIX server platform. Itwill be understood that the server communication system 42 may compriseother communication formats within the scope of the present invention.

[0033] In one embodiment, the electronic commerce applications 44 maycomprise an electronic mail application 52, a web server application 54,and a file transfer application 56. It will be understood that theserver system 12 may comprise other electronic commerce applications 44within the scope of the present invention.

[0034] The electronic mail application 52 may send and receive messagesover the networks 18. In one embodiment, the electronic mail application52 may comprise HP OPENMAIL SERVER by Hewlett-Packard Company. In thisembodiment, the electronic mail application 52 may send or receivemessages over the X.400 electronic mail network 24 (FIG. 1). It will beunderstood that the server system 12 may comprise other electronic mailapplications 52 within the scope of the present invention.

[0035] The web server application 54 may connect to and browse thenetworks 18. The web server application 54 may send and receive dataover a public network, an intranet, an extranet, and the like. The webserver application 54 may also access a shared resource, a value addednetwork (VAN) and the like over a network. In one embodiment, thebrowser 54 may comprise NETSCAPE COMMERCE SERVER by NetscapeCommunication Corporation. It will be understood that the web serverapplication 54 may comprise other browsers capable of connecting andbrowsing networks 18 within the scope of the present invention.

[0036] The web server application 54 may access the networks 18 througha fire wall 58. In one embodiment, access to public networks such as thepublic Internet 20 may be routed through the fire wall 58. It will beunderstood that access to other networks may be routed through the firewall 58 within the scope of the present invention.

[0037] The file transfer application 56 may transmit and receive datafiles over the networks 18. The file transfer application 56 may collectand distribute data files from a client directory 60. The clientdirectory 60 may comprise a collection sub-directory 62 and adistribution sub-directory 64. Files downloaded from the networks 18 maybe held in the collection sub-directory 62 prior to being downloaded tothe client system 14. Files uploaded from the client system 14 may beheld in the distribution sub-directory 64 prior to transmission over thenetworks 18. It will be understood that data files may be otherwisestored or transmitted “on-the-fly” (in real time or near real time) bythe server system 14 within the scope of the present invention.

[0038] The file transfer application 56 may download data files from thecollection sub-directory 62 to the client system 14 upon a request bythe client. As described in more detail below, the request may beautomatic upon a client logon to the server system 12 or other type ofevent.

[0039] The file transfer application may periodically scan thedistribution sub-directory 64 for data files to be transmitted over thenetworks 18. In one embodiment, the file transfer application 56 mayscan the distribution sub-directory 64 every fifteen (15) minutes. Itwill be understood that the file transfer application 56 may otherwisescan the distribution sub-directory 64 within the scope of the presentinvention.

[0040] The file transfer application 56 may call a translator 66 totranslate data files received or to be transmitted over the networks 18.The translator 66 may translate preset types of data files betweenidentified trading partners. The data files may be translated to becompatible with the recipient system. In one embodiment, data filesreceived from the networks 18 may be translated on the fly prior tobeing stored in the collection sub-directory 62. Similarly, data filesuploaded from the client system 14 may be stored in the distributionsub-directory 64 and later translated if necessary prior to beingdelivered to a trading partner. It will be understood that data filesmay be otherwise translated in the scope of the present invention.

[0041] The server security system 46 may provide validation of theclient system 14. In one embodiment, the server security system 46 mayvalidate a user identifier and a system identifier of the client system14. As described in more detail below, the user identifier may be acombination of a user ID and password. The system identifier may be acombination of a software serial number and a random number previouslygenerated and downloaded by the server security system 46. The randomnumber in conjunction with the serial number prevents the software ofthe client system 14 from being copied and used on another system.

[0042] The server security system 46 may comprise a profile informationtable 70, an application table 72 and a computer table 74. The profileinformation table 70 may store user preferences. The preferences mayinclude automatic downloads, automatic logoffs, and the like. It will beunderstood that other client preferences may be stored in profileinformation table 70. It will be further understood that the serversecurity system 46 may comprise other or different information tables inthe scope of the present invention.

[0043] The application table 72 may comprise application identifiers foreach client system. The application identifiers may be downloaded by theserver security system 46 to the client system 14 upon validation. Theapplication identifiers enable the client system 14 to access theelectronic mail application 52, the web server application 54, and thefile transfer application 56 to conduct electronic commerce over thenetworks 18. In one embodiment, the application identifiers may includean ID and password for each electronic commerce application. It will beunderstood that the application identifiers may comprise other fieldswithin the scope of the present invention.

[0044] The server security system 46 may periodically update theapplication identifiers to prevent unauthorized access to theapplications. In one embodiment, the application identifiers may beupdated every thirty (30) days. It will be understood that theidentifiers may be otherwise updated within the scope of the presentinvention.

[0045] The computer table 74 may comprise a serial number of thesoftware of each client system 14. The last random number downloaded toa client system 14 may also be stored in the computer table 74. Theserial and random numbers may be compared to serial and random numbersprovided by the client system 14 for system validation. If the numbersmatch, the system is valid. If the numbers do not match, the system isnot valid and access to the server system 12 may be denied.

[0046] In one embodiment, the server security system 46 may comprisePERL scripts and MICROSOFT VISUAL C++ version 1.5. It will be understoodthat the server security system 46 may comprise other programmingformats within the scope of the present invention.

[0047] The client system 14 may comprise an input/output system 80, aprocessor 82 and memory 84. As previously described in connection withthe input/output system 30, the input/output system 80 may connect thededicated network 16 and other input and output devices to the clientsystem 14. The dedicated network 16 may be directly connected to theclient system 14 or may be connected through a data transmission devicesuch as a modem or the like. Input devices may include a pointing devicesuch as a mouse or trackpad, a keyboard, and the like. Output devicesmay include a monitor, a printer, and the like.

[0048] The client system 14 includes computer software that may beloaded and/or downloaded into memory 84 and executed by the processor82. The computer software may generally be identified by modules andsimilar systems in memory 84. It will be understood that the computersoftware may be otherwise combined and/or divided for processing withinthe scope of the present invention. Accordingly, the labels of themodules and other software systems are for illustrative purposes and maybe varied within the scope of the present invention.

[0049] As previously described in connection with memory 34, computersoftware may be loaded into memory 84 from disk storage (not shown).Disks storage may include a variety of types of storage media. Forexample, disk storage may include floppy disk drives, hard disk drives,CD/ROM drives or magnetic tape drives.

[0050] Memory 84 may include an operating system 86, a clientcommunication system 88 and an integrated service manager 90. Theoperating system 86 may include a graphical user interface (GUI) 92capable of generating a plurality of application windows 94. Theoperating system 86 may be MacIntosh OS, WINDOWS NT, WINDOWS 95, OS/2,or any other operating system capable of providing or operating inconjunction with a graphical user interface (GUI).

[0051] The client communication system 88 may operate in conjunctionwith the server communication system 42 to provide a communicationinfrastructure between the client system 14 and the server system 12. Aspreviously discussed in connection with the server communication system42, the client communication system 88 may comprise TCP/IP for Windows,SDK-Visual Edition, part number: TCP/107S version 4.0. It will beunderstood that the client communication system 88 may comprise othercommunication formats compatible with the server communication system 42within the scope of the present invention.

[0052] The integrated service manager 90 may comprise a user interface92 for interacting with a client. As described in more detail below inconnection with FIG. 4, the user interface 92 may comprise iconsassociated with modules of the service manager 90. Modules may include alogon module 94 and a set of electronic commerce modules 96. Thus, theclient may click on icons to logon to the server system 12 and toconduct electronic commerce transactions via the server system 12.Accordingly, the client may conduct all of its electronic commercetransactions from a single interface. As a result, a client need notlocate and launch a number of separate applications, which can betime-consuming and confusing to an unsophisticated small businessclient.

[0053] The logon module 94 may invoke a client security system 100 tologon to the server system 12. The client security system 100 mayoperate in conjunction with the server security system 46 to validatethe client system 14. In one embodiment, the client security system 100may request a user identifier from the client. The user identifier maybe a user identifier (ID) and a password. The client security system 100may pass the user identifier to the server security system 46 forvalidation. The client security system 100 may also pass a systemidentifier to the server security system 46 for validation. In oneembodiment, the system identifier may comprise a serial number 102 and arandom number 104 of the client system software. A new random number isgenerated and downloaded by the server security system 46 with eachvalidation.

[0054] Upon validation of the client system 14, the client securitysystem 100 may receive application identifiers 106 from the serversecurity system 46. The application identifiers 106 enable theintegrated service manager 90 to access the electronic mail application52, the web server application 54, and the file transfer application 56on the server system 12. In one embodiment, the application identifiersmay comprise an ID and password for each application. As previouslydescribed in connection with the server security system 46, the IDs andpasswords may be periodically updated by the server security system 46to lessen or prevent unauthorized use of the applications 44.

[0055] The electronic commerce modules 96 may include a module for eachelectronic commerce application 44 of the server system 12. In oneembodiment, the modules 96 may comprise an electronic mail module 110, abrowser module 112, and a file transfer module 114. It will beunderstood that the electronic commerce modules 96 may comprise othermodules within the scope of the present invention.

[0056] The electronic mail module 110 may be launched by an electronicmail icon (FIG. 4) of the user interface 92 of the service manager 90.Upon activation, the electronic mail module 110 may open an electronicmail user interface 116 to access the electronic mail application 52.Thereafter, the client may interact directly with the applicationthrough the application interface 116.

[0057] The browser module 112 may be launched by a browser icon (FIG. 4)of the user interface 92 of the service manager 90. Upon activation, thebrowser module 112 may open a browser user interface 118 to access theweb server application 54. Thereafter, the client may interact directlywith the web server application 54 through the application interface118.

[0058] A browser extension 120 may be provided on the client system 14for reading specific types of Web pages. In one embodiment, the browserextension 120 may comprise ACROBAT READER version 2.1 by Adobe SystemsInc., which provides cross-platform capabilities. It will be understoodthat other or no browser extensions 120 may be provided within the scopeof the present invention.

[0059] The file transfer module 114 may be launched by a file transfericon (FIG. 4) of the user interface 92 of the service manager 90. Uponthe activation, the file transfer module 114 may open a file transferuser interface 122 to access the file transfer application 56.Thereafter, the client may interact directly with the file transferapplication 56 through the application interface 122.

[0060] The file transfer application 56 may download files to an inbox124 of the client system 14. The inbox 124 prevents pre-existing filesand data of the client system 14 from being overwritten by the filetransfer application 56 during file download. In one embodiment, theinbox 124 may be a dedicated directory. It will be understood that theinbox 124 may be otherwise configured within the scope of the presentinvention.

[0061] In one embodiment, the service manager 90 may comprise MICROSOFTVISUAL BASIC version 3.0. In this embodiment, the user interface 92,logon module 94 and electronic commerce modules 96 may also compriseMICROSOFT VISUAL BASIC version 3.0. It will be understood that theintegrated service manager 90, user interface 92 and modules 94 and 96may comprise other programming formats and remain within in the scope ofthe present invention.

[0062] A virus protection application 130 may also be provided inmemory. The virus protection application 130 may be operated by theclient system 14 to scan downloaded data for harmful viruses and thelike. In one embodiment, the virus protection application 130 maycomprise F-PROT PROFESSIONAL version 2.22.2 for DOS/Wind3.X/Win95 byCommand Software Systems. In this embodiment, the virus protectionapplication 130 may be set to selectively or continually monitor theclient system 14. It will be understood that other or no virusprotection applications may be used and remain within the scope of thepresent invention.

[0063] The client system 14 may include a tutorial 132 in memory 84. Thetutorial may provide information to the client on how to operate theintegrated service manager 90. The tutorial 132 may be accessed throughthe integrated service manager 90. In one embodiment, the tutorial 132may be accessed through an icon (FIG. 4) of the user interface 92 of theservice manager 90. The tutorial 132 may be programmed using XVTDEVELOPMENT SOLUTIONS FOR C by XVT Software, Inc. It will be understoodthat the tutorial 132 may be otherwise programmed or accessed within thescope of the present invention.

[0064] The client system 14 may also provide a customer assistancemodule 134 for the client. Customer assistance may allow the client toquickly and easily obtain help for configuring and using the integratedelectronic commerce system 10. In one embodiment, the customerassistance module 134 may be accessed through an icon (FIG. 4) of theuser interface 92 of the service manager 90.

[0065]FIG. 3 illustrates a flow diagram by which a client may conductelectronic commerce in accordance with one embodiment of the presentinvention. The process begins at step 150 in which a client may initiatelogon to the server system 12. As previously described, the client mayinitiate logon by clicking on a logon icon of the user interface 92 ofthe service manager 90. In response, as described in more detail below,the client security system 100 may display a dialog box to the clientrequesting a user identifier from the client. The user identifier maycomprise a user ID and a password.

[0066] Proceeding to step 152, the client may enter a user ID. At step154, the client may enter a password. The client security system 100 maythen pass the user ID and password to the server system 12 forvalidation. Upon validation, the client system 14 may display the userinterface 92 of the service manager 90.

[0067] Referring to FIG. 4, the user interface 92 may comprise anapplication window 170. Application window 170 may comprise drop downmenus 172, toolbar 174 and a plurality of icons 176 for selectingelectronic commerce services. For the embodiment of FIG. 4, the window170 may comprise a logon icon 180, an electronic mail icon 182, aplurality of browser icons 184, and a file transfer icon 186. The logonicon 180 may be associated with the logon module 94 of the servicemanager 90. The electronic mail icon 182 may be associated with theelectronic mail module 110 of the service manager 90. The browser icons184 may be associated with the browser module 112 of the service manager90. Several browser icons 184 may be provided to divide browser servicesinto specific network services. For example, Internet access may have aseparate icon from intranet access. Further, intranet access may bedivided into specific value added networks (VAN) such as onlineregulations, regulatory rulings and the like, databases, and aparticular company's intranet. It will be understood that the browsericons 184 may be otherwise divided within the scope of the presentinvention. The file transfer icon 186 may be associated with the filetransfer module 114 of the service manager 90.

[0068] The application window 170 may include additional icons withinthe scope of the present invention. For example, the application window170 may include a tutorial icon 190 and a customer assistance icon 192.The tutorial icon 190 may be associated with the tutorial 132.Similarly, the customer assistance icon 192 may be associated withcustomer assistance 134. It will be understood that fewer or differenticons may be provided in the user interface 92 of the service manager90.

[0069] Returning to FIG. 3, the client may select electronic mailservices from the application window 170 displayed at state 156. Aspreviously described, the client may select electronic mail by clickingon the electronic mail icon 182. The electronic mail selection branch ofstate 156 leads to state 158. At state 158, the client may send, receiveand/or check electronic mail messages. After the client has finished,the quit electronic mail branch of state 158 may return to state 156.

[0070] The client may also select browser services from the applicationwindow 170 displayed at state 156. As previously described, the clientmay select the browser by clicking on one of the browser icons 184. Thebrowser selection branch of state 156 leads to state 160. At state 160,the client may browse the selected network 18. As previously described,the network may be a value added network (VAN) , an intranet, extranet,Internet, and the like. After the client has finished browsing theselected network 18, the quit browser branch of state 160 may return tostate 156.

[0071] The client may further select file transfer services from theapplication window 170 displayed at state 156. As previously described,the client may select file transfer services by clicking on the filetransfer icon 186. The file transfer selection branch of state 156 leadsto state 162. At state 162, the client may transmit and receive datafiles over the networks 18. As previously described, the data files mayinclude electronic data interchange (EDI), electronic funds transfer(EFT), and the like. After the client has finished transferring funds,the quit file transfer branch of state 162 may return to state 156.

[0072] Accordingly, the client may access a wide variety of electroniccommerce services from a single interface. As a result, smaller andnon-sophisticated businesses may participate in electronic commerceservices. Such participation improves the efficiency of the smallerbusinesses and of larger businesses that may now electronically tradewith the smaller businesses.

[0073] After the client has finished its electronic commercetransactions, the client may logoff the server system 12. The logoffselection branch of state 156 leads to the end of the process.

[0074]FIG. 5 illustrates a flow diagram of a method of providingelectronic commerce services in accordance with one embodiment of thepresent invention. The process begins at step 200 in which the clientsystem 14 may receive an initiation event. As previously described, theinitiation event may be a client clicking on the logon icon 180 of theuser interface 92 of the service manager.

[0075] Proceeding to step 202, the client security system 100 mayreceive a user identifier. As previously described, the user identifiermay be received from the client in response to a request by the clientsecurity system 100. The user identifier may comprise a user ID and apassword. At step 204, the client security system 100 may retrieve asystem identifier. The system identifier may be a serial number 102 anda random number 104 of the client system software. Proceeding to step206, the client security system 100 may upload the user and systemidentifiers to the server system 12. Communication between the clientsystem 14 and the server system 12 may be carried out by the server andclient communication systems 42 and 88.

[0076] Next, at step 208, the server security system 46 may validate theuser identifier. As previously described, the user identifier is validif the user ID and password matches that stored in the server system 12.At step 210, the server security system 46 may validate the systemidentifier. The system identifier is valid if the serial and randomnumbers 102 and 104 of the software matches that stored in the serversystem 12. If the user identifier and/or the system identifier isinvalid, access to the server system 12 may be denied.

[0077] Proceeding to step 212, upon validation the server securitysystem 46 may retrieve profile information and application identifiersassociated with the client system 14. The profile information may beretrieved from the profile information table 70. The applicationidentifiers may be retrieved from the application table 72. Aspreviously described, the application identifiers may comprise an ID andpassword for each electronic commerce application of the system 10.

[0078] At step 214, the server security system 46 may generate a randomnumber to be used for validation the next time the client attempts tologon to the server system 12. The random number is a safeguard toprevent unauthorized copying and use of the client system software.Next, at step 216, the application identifiers and the random number maybe downloaded to the client system 14. The application identifiersenable the client system 14 to access the electronic commerceapplications of the server system 12. Accordingly, the electroniccommerce system 10 provides a single point of entry for the client toelectronic commerce systems. As a result, the client need only remembera single user identifier rather than identifiers for several differentelectronic commerce applications.

[0079] Step 216 leads to state 218. At state 218, the service manager 90may display the user interface 92. As previously described, the userinterface 92 may be the application window 170 described in connectionwith FIG. 4. In response to receipt of an electronic mail selection atstate 218, the electronic mail branch of state 218 may lead to step 220.At step 220, the electronic mail application 52 may be invoked. Next, atstep 222, the electronic mail identifier may be provided to theelectronic mail application 52 to enable access to the application.After the application has been accessed, the client may work directlywith the application. Accordingly, step 222 returns to state 218 whereinthe user interface 92 of the service manager 90 is displayed.

[0080] In response to receipt of a browser selection at state 218, thebrowser branch of state 218 may lead to step 224. At step 224, the webserver application 54 may be invoked. Next, at step 226, the browseridentifier may be provided to access the web server application 54. Atstep 228, a fire wall identifier for the browser may also be provided.Proceeding to step 230, the fire wall identifier may be validated toallow the browser to access a public network through the fire wall 58.After the web server application 54 has been accessed, the client maywork directly with the application. Step 230 returns to state 218wherein the user interface 92 of the service manager 90 is displayed.

[0081] In response to receipt of a file transfer selection at state 218,the file transfer branch of state 218 may lead to step 232. At step 232,the file transfer application 56 may be invoked. Next, at step 234, thefile transfer identifier may be provided to access the file transferapplication 56. After the file transfer application 56 has beenaccessed, the client may work directly in the application. Step 234returns to state 218 wherein the user interface 92 of the servicemanager 90 is displayed.

[0082] In response to a logoff selection at state 218, the logoff branchof state 218 may lead to step 240. At step 240, the client system 14 maylogoff of the server system 12. Step 240 leads to the end of theprocess.

[0083]FIG. 6 illustrates a flow diagram of a method of uploading andtransmitting a client data file over the network 18 in accordance withone embodiment of the present invention. As previously described, thedata file may comprise an electronic data interchange (EDI) file, anelectronic funds transfer (EFT) file, and the like. The process beginsat step 250 in which the file transfer application 56 receives arecipient address for a data file through the file transfer userinterface 122. Next, at step 252, the file transfer application 56 mayreceive the name of the data file through the user interface 122.

[0084] Proceeding to step 254, the data file may be retrieved on theclient system 14. At step 256, the file transfer application 56 mayupload the data file and the recipient address to the server system 12.Next, at decisional step 258, it is determined if the data file is to betranslated. As previously described, preset types of data files betweenidentified training partners may be translated to be compatible with therecipient system. For example, a file may be translated in accordancewith a data format required by a particular trading partner. If the datafile is to be translated, the YES branch of decisional step 258 leads tostep 260.

[0085] At step 260, the translation protocol for the data file isretrieved. Next, at step 262, the translator 66 may translate the datafile. Step 262 continues to step 264. Returning to decisional step 258,if the data file is not to be translated, the NO branch of decisionalstep 258 also leads to step 264.

[0086] At step 264, the file transfer application 56 may temporarilyhold the data file in the distribution sub-directory 64 of clientdirectory 60. Proceeding to step 266, the file transfer application 56may periodically check the distribution sub-directories 64 for files tobe transmitted over the networks 18. In one embodiment, the filetransfer application 56 may check the distribution sub-directory 64every fifteen (15) minutes. It will be understood that file transferapplication 56 may otherwise check the distribution sub-directory 64within the scope of the present invention. Proceeding to step 268, thefile transfer application 56 may transmit the data file over thenetworks 18 to the recipient address. Step 268 leads to the end of theprocess.

[0087]FIG. 7 illustrates a flow diagram of a method of receiving anddownloading a data file from a network to a client system in accordancewith one embodiment of the present invention. As previously described,the data file may be an electronic data interchange (EDI) file, anelectronic funds transfer (EFT) file, and the like. The process beginsat step 300 wherein a data file is received over the networks 18. Next,at step 302, the address of the file is also received. Step 302 leads todecisional step 304.

[0088] At decisional step 304, the file transfer application 56 maydetermine if the data file is to be translated. As previously described,preset types of data files between identified trading partners may betranslated to be compatible with the recipient's system. If the datafiles are to be translated, the YES branch of decisional step 304 leadsto step 306.

[0089] At step 306, a translation protocol for the data file isretrieved. Proceeding to step 308, the translator 66 may translate thedata file. Step 308 leads to step 310. Returning to decisional step 304,if the data file is not to be translated, the NO branch of decisionalstep 304 also leads to step 310.

[0090] At step 310, the file transfer application 56 may temporarilyhold the data file in a collection sub-directory 62. Next, at step 312,the file transfer application 56 may receive a request to download thedata file to the client system 14. The request may be an automatic,periodic or manual request from the client.

[0091] Next, at step 314, the file transfer application 56 may downloada data file from the collection sub-directory 62 to the inbox 124 of theclient system 14. Use of the inbox 124 will prevent the file transferapplication 56 from overwriting other files or data of the client system14. At this point the process ends.

[0092] Although the present invention has been described with severalembodiments, various changes and modifications may be suggested to oneskilled in the art. It is intended that the present invention encompasssuch changes and modifications as fall within the scope of the appendedclaims.

What is claimed is:
 1. A method comprising: providing an electroniccommerce application at a server; providing a first user interface at aclient having an icon associated with a module at the client and theelectronic commerce application; validating, at the server, the clientusing an identifier associated with the client and validating a userassociated with the client in response to clicking the icon; andallowing a second user interface to access the electronic commerceapplication on the server based on the validation of the client and thevalidation of the user.
 2. The method according to claim 1 and furthercomprising activating, by the module, the second user interface at theclient in response to clicking the icon.
 3. The method according toclaim 1, wherein the module comprises a logon module.
 4. The methodaccording to claim 1, wherein the second user interface comprises anapplication window.
 5. The method according to claim 1, wherein a useridentifier associated with the user is requested at the second userinterface at the client.
 6. The method according to claim 1, whereinvalidating the user further comprises uploading a user identifier fromthe client system to the server system.
 7. The method according to claim1, wherein the module is at the client.
 8. The method according to claim1, wherein the identifier was previously downloaded from the server tothe client.
 9. The method according to claim 1, wherein the electroniccommerce application comprises any of an electronic mail application, aweb server application or a file transfer application.
 10. The methodaccording to claim 1 and further comprising validating access of theclient system to a firewall.
 11. The method according to claim 1,wherein the identifier comprises a serial number.
 12. The methodaccording to claim 1, wherein the identifier comprises a random number.13. The method according to claim 1, wherein validating the identifiercomprises uploading the identifier from the client to the server. 14.The method according to claim 1 and further comprising retrievingprofile information associated with the client from the server.
 15. Themethod according to claim 1 and further comprising: generating a newidentifier in response to validation of the identifier; and downloadingthe new identifier to the client.
 16. The method according to claim 1,wherein the electronic commerce application comprises a file transferapplication operable to send and receive electronic data interchange(EDI) data over the network.
 17. A system comprising: software operableto: provide an electronic commerce application at a server; provide afirst user interface at a client having an icon associated with a moduleat the client and the electronic commerce application; validate, at theserver, the client using an identifier associated with the client andvalidating a user associated with the client in response to clicking theicon; and allow a second user interface to access the electroniccommerce application on the server based on the validation of the clientand the validation of the user.
 18. The system according to claim 17,wherein the software is further operable to activate, by the module, thesecond user interface at the client in response to clicking the icon.19. The system according to claim 17, wherein the module comprises alogon module.
 20. The system according to claim 17, wherein the seconduser interface comprises an application window.
 21. The system accordingto claim 17, wherein a user identifier associated with the user isrequested at the second user interface at the client.
 22. The systemaccording to claim 17, wherein validating the user further comprisesuploading a user identifier from the client system to the server system.23. The system according to claim 17, wherein the module is at theclient.
 24. The system according to claim 17, wherein the identifier waspreviously downloaded from the server to the client.
 25. The systemaccording to claim 17, wherein the electronic commerce applicationcomprises any of an electronic mail application, a web serverapplication or a file transfer application.
 26. The system according toclaim 17, wherein the software is further operable to validate access ofthe client system to a firewall.
 27. The system according to claim 17,wherein the identifier comprises a serial number.
 28. The systemaccording to claim 17, wherein the identifier comprises a random number.29. The system according to claim 17, wherein validating the identifiercomprises uploading the identifier from the client to the server. 30.The system according to claim 17 and further comprising retrievingprofile information associated with the client from the server.
 31. Thesystem according to claim 17, wherein the software is further operableto: generate a new identifier in response to validation of theidentifier; and download the new identifier to the client.
 32. Thesystem according to claim 17, wherein the electronic commerceapplication comprises a file transfer application operable to send andreceive electronic data interchange (EDI) data over the network.
 33. Asystem comprising: means for providing an electronic commerceapplication at a server; means for providing a first user interface at aclient having an icon associated with a module at the client and theelectronic commerce application; means for validating, at the server,the client using an identifier associated with the client and validatinga user associated with the client in response to clicking the icon; andmeans for allowing a second user interface to access the electroniccommerce application on the server based on the validation of the clientand the validation of the user.
 34. A method comprising: providing anelectronic commerce application at a server; providing a first userinterface at a client having an icon associated with a module at theclient and the electronic commerce application; activating, by themodule, a second user interface at the client in response to clickingthe icon; validating the client at the server using an identifierpreviously downloaded to the client; validating a user associated withthe client at the server; and allowing the second user interface toaccess the electronic commerce application on the server based on thevalidation of the client and the validation of the user.
 35. The methodaccording to claim 34, wherein the module comprises a logon module atthe client.
 36. The method according to claim 34, wherein the electroniccommerce application comprises any of an electronic mail application, aweb server application or a file transfer application.
 37. The methodaccording to claim 34, wherein validating the user further comprisesuploading a user identifier from the client system to the server system.38. The method according to claim 34, wherein the identifier comprises aserial number.
 39. The method according to claim 34, wherein theidentifier comprises a random number.
 40. The method according to claim34, wherein validating the identifier comprises uploading the identifierfrom the client to the server.
 41. The method according to claim 34 andfurther comprising retrieving profile information associated with theclient.
 42. The method according to claim 34 and further comprising:generating a new identifier in response to validation of the identifier;and downloading the new identifier to the client.
 43. The methodaccording to claim 34, wherein the electronic commerce applicationcomprises a file transfer application operable to send and receiveelectronic data interchange (EDI) data over the network.
 44. A systemcomprising: software operable to: provide an electronic commerceapplication at a server; provide a first user interface at a clienthaving an icon associated with a module at the client and the electroniccommerce application; activate, by the module, a second user interfaceat the client in response to clicking the icon; validate the client atthe server using an identifier previously downloaded to the client;validate a user associated with the client at the server; and allow thesecond user interface to access the electronic commerce application onthe server based on the validation of the client and the validation ofthe user.
 45. The system according to claim 44 wherein the modulecomprises a logon module at the client.
 46. The system according toclaim 44, wherein the electronic commerce application comprises any ofan electronic mail application, a web server application or a filetransfer application.
 47. The system according to claim 44, wherein thesoftware is further operable to upload a user identifier from the clientsystem to the server system.
 48. The system according to claim 44,wherein the identifier comprises a serial number.
 49. The systemaccording to claim 44, wherein the identifier comprises a random number.50. The system according to claim 44, wherein validating the identifiercomprises uploading the identifier from the client to the server. 51.The system according to claim 44, wherein the software is furtheroperable to retrieve profile information associated with the client. 52.The system according to claim 44, wherein the software is furtheroperable to: generate a new identifier in response to validation of theidentifier; and download the new identifier to the client.
 53. Thesystem according to claim 44, wherein the electronic commerceapplication comprises a file transfer application operable to send andreceive electronic data interchange (EDI) data over the network.
 54. Asystem comprising: means for providing an electronic commerceapplication at a server; means for providing a first user interface at aclient having an icon associated with a module at the client and theelectronic commerce application; means for activating, by the module, asecond user interface at the client in response to clicking the icon;means for validating the client at the server using an identifierpreviously downloaded to the client; means for validating a userassociated with the client at the server; and means for allowing thesecond user interface to access the electronic commerce application onthe server based on the validation of the client and the validation ofthe user.
 55. A method comprising: providing an electronic commerceapplication at a server; providing a first user interface at a clienthaving an application icon and a logon icon; validating the client atthe server using an identifier previously downloaded to the client inresponse to clicking the logon icon; validating a user associated withthe client at the server in response to clicking the logon icon;activating, by the module, a second user interface at the client inresponse to clicking the application icon; and allowing the second userinterface to access the electronic commerce application on the serverbased on the validation of the client and the validation of the user.56. The method according to claim 55, wherein the second user interfacecomprises an application window.
 57. The method according to claim 55,wherein the identifier comprises a serial number.
 58. The methodaccording to claim 55, wherein the electronic commerce applicationcomprises any of an electronic mail application, a web serverapplication or a file transfer application.
 59. A system comprising:software operable to: provide an electronic commerce application at aserver; provide a first user interface at a client having an applicationicon and a logon icon; validate the client at the server using anidentifier previously downloaded to the client in response to clickingthe logon icon; validate a user associated with the client at the serverin response to clicking the logon icon; activate, by the module, asecond user interface at the client in response to clicking theapplication icon; and allow the second user interface to access theelectronic commerce application on the server based on the validation ofthe client and the validation of the user.
 60. The system according toclaim 59, wherein the second user interface comprises an applicationwindow.
 61. The system according to claim 59, wherein the identifiercomprises a serial number.
 62. The system according to claim 59, whereinthe electronic commerce application comprises any of an electronic mailapplication, a web server application or a file transfer application.63. A system comprising: means for providing an electronic commerceapplication at a server; means for providing a first user interface at aclient having an application icon and a logon icon; means for validatingthe client at the server using an identifier previously downloaded tothe client in response to clicking the logon icon; means for validatinga user associated with the client at the server in response to clickingthe logon icon; means for activating, by the module, a second userinterface at the client in response to clicking the application icon;and means for allowing the second user interface to access theelectronic commerce application on the server based on the validation ofthe client and the validation of the user.